-
Notifications
You must be signed in to change notification settings - Fork 1.4k
doc: Add 3.1.1 release to main #24573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 08c5f27866102482b355e2e724c409c687771f8c more detailssdk-nrf:
Github labels
List of changed files detected by CI (6)Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
|
You can find the documentation preview for this PR here. Preview links for modified nRF Connect SDK documents: https://ncsdoc.z6.web.core.windows.net/PR-24573/nrf/protocols/matter/index.html |
30b0672 to
0b60156
Compare
0b60156 to
8873fd8
Compare
|
The table in the nrf/protocols/matter/index.rst page also requires an update. |
8873fd8 to
f72dbc4
Compare
|
Please add known issue under MCUBoot: NCSDK-35259 Upgrade failed when enabled encryption Affected platforms: nRF54LM20 Encryption for nRF54LM20 is currently not supported .... NCSDK-34251 Device will not boot when Hardware Downgrade Prevention reaches number of available upgrades Affected platforms: nRF54LM20 Workaround: Cherry-pick #23779 |
f72dbc4 to
41807c2
Compare
41807c2 to
ac9baa0
Compare
Done, please check @maciejpietras. |
ac9baa0 to
2ba089d
Compare
Add 3.1.1 release to main Signed-off-by: Richa Pandey <[email protected]>
2ba089d to
08c5f27
Compare
|
@nrfconnect/ncs-code-owners Please review. |
|
The compliance failure is false-positive, yet another time it reports unreachable link, but it's just fine:
|
Add 3.1.1 release to main